Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f4cb65bde4546124162d10929c6d7bc4e5e495a33efbe264df7404c51ec425d

Tx prefix hash: f2a9033663d747b85ae6ef0d5a2d5beb2954809393db24596bf657cbab4a2067
Tx public key: feeae4c2df135524419752b3c1ae6dc040f062cac75c8dfeada6a9f9ebd21ad6
Timestamp: 1671847673 Timestamp [UCT]: 2022-12-24 02:07:53 Age [y:d:h:m:s]: 02:026:08:35:59
Block: 659230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540743 RingCT/type: yes/0
Extra: 01feeae4c2df135524419752b3c1ae6dc040f062cac75c8dfeada6a9f9ebd21ad602110000000833af99f4000000000000000000

1 output(s) for total of 4.015108851000 dcy

stealth address amount amount idx
00: 5081ad4a3052729e8d24e580c4d29926124ee019a0473da54899aa76a0d8fba2 4.015108851000 1099929 of 0

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": 659240, "vin": [ { "gen": { "height": 659230 } } ], "vout": [ { "amount": 4015108851, "target": { "key": "5081ad4a3052729e8d24e580c4d29926124ee019a0473da54899aa76a0d8fba2" } } ], "extra": [ 1, 254, 234, 228, 194, 223, 19, 85, 36, 65, 151, 82, 179, 193, 174, 109, 192, 64, 240, 98, 202, 199, 92, 141, 254, 173, 166, 169, 249, 235, 210, 26, 214, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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