Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 72f4839c71da3f4d0c1d1e9844f4f21310e1c6c9fb6fc50ca8a8c7a1b70b9009

Tx prefix hash: bb4380b302443cc7b062503d4e6949c43646815b01ac43bbb2efce9711b691aa
Tx public key: 1f5ced9de5748d62a414a8956ce22545820c4ea8f909e7a894d2f3e16536c259
Timestamp: 1705993545 Timestamp [UCT]: 2024-01-23 07:05:45 Age [y:d:h:m:s]: 01:090:18:48:30
Block: 941401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325991 RingCT/type: yes/0
Extra: 011f5ced9de5748d62a414a8956ce22545820c4ea8f909e7a894d2f3e16536c2590211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ffdb80462ff9dbc061ec1fc4d65a51d4094a756b51bc2db8e54e8612dfd4000 0.600000000000 1399547 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 941411, "vin": [ { "gen": { "height": 941401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ffdb80462ff9dbc061ec1fc4d65a51d4094a756b51bc2db8e54e8612dfd4000" } } ], "extra": [ 1, 31, 92, 237, 157, 229, 116, 141, 98, 164, 20, 168, 149, 108, 226, 37, 69, 130, 12, 78, 168, 249, 9, 231, 168, 148, 210, 243, 225, 101, 54, 194, 89, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8