Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ea6e2eeef3e921c1633370a040fb01839a8576d6baef77baf51a68487dc4e31

Tx prefix hash: d38040a6dfa2cffa7a62eec1f06c2b47ee0d14865335a343f2de5cd5af0194eb
Tx public key: b67000fee4cd424783579c0a69139ef85e02dfc3ac8fbe4241d6739f977c67e6
Timestamp: 1712883513 Timestamp [UCT]: 2024-04-12 00:58:33 Age [y:d:h:m:s]: 00:234:16:46:03
Block: 998534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168039 RingCT/type: yes/0
Extra: 01b67000fee4cd424783579c0a69139ef85e02dfc3ac8fbe4241d6739f977c67e60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9939189b6601bfd47d7c7d04f3dcbe5e0f7764ca5ef2dbc9ea165a5f96937e3 0.600000000000 1458986 of 15

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": 998544, "vin": [ { "gen": { "height": 998534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9939189b6601bfd47d7c7d04f3dcbe5e0f7764ca5ef2dbc9ea165a5f96937e3" } } ], "extra": [ 1, 182, 112, 0, 254, 228, 205, 66, 71, 131, 87, 156, 10, 105, 19, 158, 248, 94, 2, 223, 195, 172, 143, 190, 66, 65, 214, 115, 159, 151, 124, 103, 230, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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