Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33e873e17351f89cd4c95c642ae3e70d7f7e166aa721a9420b3accf2fe6e138

Tx prefix hash: daae88d2a4fc3438c7b614a632c5aeeb7d20fb02d9a36baec40a500b0b9b8ba7
Tx public key: efac9368496ae1672643d2eb27f1a344c2091ff156019a19ecb6a7cfa8d78598
Timestamp: 1578178494 Timestamp [UCT]: 2020-01-04 22:54:54 Age [y:d:h:m:s]: 05:038:16:08:36
Block: 38841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1177449 RingCT/type: yes/0
Extra: 01efac9368496ae1672643d2eb27f1a344c2091ff156019a19ecb6a7cfa8d7859802110000000fd81c26c0000000000000000000

1 output(s) for total of 456.356764791000 dcy

stealth address amount amount idx
00: c76a2d580b215194a7dcdd817022ee29c5a5d9adb9638abd6901a9f3c637b0ce 456.356764791000 66524 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": 38851, "vin": [ { "gen": { "height": 38841 } } ], "vout": [ { "amount": 456356764791, "target": { "key": "c76a2d580b215194a7dcdd817022ee29c5a5d9adb9638abd6901a9f3c637b0ce" } } ], "extra": [ 1, 239, 172, 147, 104, 73, 106, 225, 103, 38, 67, 210, 235, 39, 241, 163, 68, 194, 9, 31, 241, 86, 1, 154, 25, 236, 182, 167, 207, 168, 215, 133, 152, 2, 17, 0, 0, 0, 15, 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