Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd2caf358b14ad9ce9a0117fdc89ff6b818edfa393fa2391c40ca774d02b05be

Tx prefix hash: 459861bb4828ab7b7b341bb4038b3b51c033781d71311808550c820247671f00
Tx public key: d82026e6adcf91a7305470d074e7da80866ca49a3c4d18721ff4c4cc1d226873
Timestamp: 1577611526 Timestamp [UCT]: 2019-12-29 09:25:26 Age [y:d:h:m:s]: 05:148:14:56:18
Block: 34214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1256039 RingCT/type: yes/0
Extra: 01d82026e6adcf91a7305470d074e7da80866ca49a3c4d18721ff4c4cc1d22687302110000000dd81c26c0000000000000000000

1 output(s) for total of 472.754499734000 dcy

stealth address amount amount idx
00: f93f1a10084a028b49ef9ba73ef87b520f820c957588cb453ac188d4d1caf2d6 472.754499734000 57584 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": 34224, "vin": [ { "gen": { "height": 34214 } } ], "vout": [ { "amount": 472754499734, "target": { "key": "f93f1a10084a028b49ef9ba73ef87b520f820c957588cb453ac188d4d1caf2d6" } } ], "extra": [ 1, 216, 32, 38, 230, 173, 207, 145, 167, 48, 84, 112, 208, 116, 231, 218, 128, 134, 108, 164, 154, 60, 77, 24, 114, 31, 244, 196, 204, 29, 34, 104, 115, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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