Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 734e08ef71f856f509b73fbb02d879efa91ae1e1822f2dbeb264d1757bd98c5c

Tx prefix hash: dad20d66e95a80259a1f51d4924e16eb9bf44a237794dcdcd69145b83300d2a2
Tx public key: 41235119d5e5ed821b40af09ddbfccaee497afad6cdee6d6ae06afd95ce2f7d3
Timestamp: 1756903443 Timestamp [UCT]: 2025-09-03 12:44:03 Age [y:d:h:m:s]: 00:079:10:28:12
Block: 1360472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56796 RingCT/type: yes/0
Extra: 0141235119d5e5ed821b40af09ddbfccaee497afad6cdee6d6ae06afd95ce2f7d3021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f47e90f5ef34de74a682db38d6d9b062b160ef0c3a9fbda3c913820e1ad1a98 0.600000000000 1848485 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": 1360482, "vin": [ { "gen": { "height": 1360472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f47e90f5ef34de74a682db38d6d9b062b160ef0c3a9fbda3c913820e1ad1a98" } } ], "extra": [ 1, 65, 35, 81, 25, 213, 229, 237, 130, 27, 64, 175, 9, 221, 191, 204, 174, 228, 151, 175, 173, 108, 222, 230, 214, 174, 6, 175, 217, 92, 226, 247, 211, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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