Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574dbdc143deaf4332d22eb886c712d8ab98bd40535f067ef3ca61a67ffbc0d3

Tx prefix hash: 98f60178c2ce0e9c2e85777b69a8017fa567b56caad06fcbe79597549dcf5f67
Tx public key: fa5d87160578a9524a751301ca0a4d1f5f4238ac2adcd7c30fa5b9dc367fa9ac
Timestamp: 1577809978 Timestamp [UCT]: 2019-12-31 16:32:58 Age [y:d:h:m:s]: 05:099:19:38:08
Block: 35888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221076 RingCT/type: yes/0
Extra: 01fa5d87160578a9524a751301ca0a4d1f5f4238ac2adcd7c30fa5b9dc367fa9ac0211000000014943cd9f000000000000000000

1 output(s) for total of 466.783185381000 dcy

stealth address amount amount idx
00: c8cd03e5ce530c455792298c8e7e7e72610650b289fdfcaa8acf76ab2d16a707 466.783185381000 60600 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": 35898, "vin": [ { "gen": { "height": 35888 } } ], "vout": [ { "amount": 466783185381, "target": { "key": "c8cd03e5ce530c455792298c8e7e7e72610650b289fdfcaa8acf76ab2d16a707" } } ], "extra": [ 1, 250, 93, 135, 22, 5, 120, 169, 82, 74, 117, 19, 1, 202, 10, 77, 31, 95, 66, 56, 172, 42, 220, 215, 195, 15, 165, 185, 220, 54, 127, 169, 172, 2, 17, 0, 0, 0, 1, 73, 67, 205, 159, 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