Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12183fea0746d495b1afe060a31333b97f31185536af24e0a224175d808c6185

Tx prefix hash: 638a852d1213dcb05ed93b574940ff7c7b4e3929188ce59b31bf13a77e20f3df
Tx public key: d7ee4cc3486b8c3adad54eddb40a444399fe3b72e4dae72401da10af33d7d006
Timestamp: 1580484936 Timestamp [UCT]: 2020-01-31 15:35:36 Age [y:d:h:m:s]: 04:332:22:36:24
Block: 55904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129150 RingCT/type: yes/0
Extra: 01d7ee4cc3486b8c3adad54eddb40a444399fe3b72e4dae72401da10af33d7d006021100000004b221b3d1000000000000000000

1 output(s) for total of 400.652323309000 dcy

stealth address amount amount idx
00: b6452ee44add64079b0c881cb3a821288cb6ec1750c03d242f542dbe8e54bbe2 400.652323309000 103132 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": 55914, "vin": [ { "gen": { "height": 55904 } } ], "vout": [ { "amount": 400652323309, "target": { "key": "b6452ee44add64079b0c881cb3a821288cb6ec1750c03d242f542dbe8e54bbe2" } } ], "extra": [ 1, 215, 238, 76, 195, 72, 107, 140, 58, 218, 213, 78, 221, 180, 10, 68, 67, 153, 254, 59, 114, 228, 218, 231, 36, 1, 218, 16, 175, 51, 215, 208, 6, 2, 17, 0, 0, 0, 4, 178, 33, 179, 209, 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