Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1e6a1fd362f82e5b0ae5c979b991cab87541f2a572c700ab69a28636e46141

Tx prefix hash: f5f08044a31f228a90d46ee6a7a8e4d55b7ad8eb7016061c4f7771c20dfeaa88
Tx public key: d615be934c8c0cae92befc4aa0528e0f5f6be923ccf19d0b2db912093e11e34d
Timestamp: 1577702385 Timestamp [UCT]: 2019-12-30 10:39:45 Age [y:d:h:m:s]: 04:332:00:56:30
Block: 34951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126426 RingCT/type: yes/0
Extra: 01d615be934c8c0cae92befc4aa0528e0f5f6be923ccf19d0b2db912093e11e34d021100000076398c17aa000000000000000000

1 output(s) for total of 470.111834959000 dcy

stealth address amount amount idx
00: 4d8258589646d268f36f85633ad600bedfbe1bb7f0979517bd1ba9802ab32f44 470.111834959000 58882 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": 34961, "vin": [ { "gen": { "height": 34951 } } ], "vout": [ { "amount": 470111834959, "target": { "key": "4d8258589646d268f36f85633ad600bedfbe1bb7f0979517bd1ba9802ab32f44" } } ], "extra": [ 1, 214, 21, 190, 147, 76, 140, 12, 174, 146, 190, 252, 74, 160, 82, 142, 15, 95, 107, 233, 35, 204, 241, 157, 11, 45, 185, 18, 9, 62, 17, 227, 77, 2, 17, 0, 0, 0, 118, 57, 140, 23, 170, 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