Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab12db76cb80fdba61421c7a372a96935148a39a5b81b76202ce928f2d1ad3b5

Tx prefix hash: b71ee6768c6bdd90b4edfd6d2e3e2585761e915f151820ac3c05af1c0c3c6e24
Tx public key: 138aedd4fb85266b312bdd1983721e0fbcfc6936adac688f4029a439404843f1
Timestamp: 1712743911 Timestamp [UCT]: 2024-04-10 10:11:51 Age [y:d:h:m:s]: 01:207:21:32:44
Block: 997380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407266 RingCT/type: yes/0
Extra: 01138aedd4fb85266b312bdd1983721e0fbcfc6936adac688f4029a439404843f1021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0272f60ba838df1c6e341837a91d5c9cecc7a9f507aa60e868f1c58afc5ef607 0.600000000000 1457812 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": 997390, "vin": [ { "gen": { "height": 997380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0272f60ba838df1c6e341837a91d5c9cecc7a9f507aa60e868f1c58afc5ef607" } } ], "extra": [ 1, 19, 138, 237, 212, 251, 133, 38, 107, 49, 43, 221, 25, 131, 114, 30, 15, 188, 252, 105, 54, 173, 172, 104, 143, 64, 41, 164, 57, 64, 72, 67, 241, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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