Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5293f45f0f8c43aa7b0447e80d2c20a1b2b410f827c558bdd63f81cfe1ecc08b

Tx prefix hash: b90fba2fdae5d2e170449e38a0cd66356e14019e53bfe74de13cf685046058f2
Tx public key: 8cbdc40f2d74f275c1fae00e494692aab875af60f1173dea292879605be759c1
Timestamp: 1720339258 Timestamp [UCT]: 2024-07-07 08:00:58 Age [y:d:h:m:s]: 00:348:03:56:11
Block: 1060372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248654 RingCT/type: yes/0
Extra: 018cbdc40f2d74f275c1fae00e494692aab875af60f1173dea292879605be759c1021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75b92c0eb622f8d34bcdf600fb1d00e97f13591d614f2761df1841d9175dda9f 0.600000000000 1530849 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": 1060382, "vin": [ { "gen": { "height": 1060372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75b92c0eb622f8d34bcdf600fb1d00e97f13591d614f2761df1841d9175dda9f" } } ], "extra": [ 1, 140, 189, 196, 15, 45, 116, 242, 117, 193, 250, 224, 14, 73, 70, 146, 170, 184, 117, 175, 96, 241, 23, 61, 234, 41, 40, 121, 96, 91, 231, 89, 193, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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