Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7d1450760b11ab291dc1a5edfef71f30e43e60b868fcb14f206b34dc0a47afd

Tx prefix hash: 341e8f13977e4e4206bce3950816e4fa5deb1a41856f79c7bc5015a15740e108
Tx public key: 0ad8b17e6904c303e9161dbba16052f8b6b2135cca84e09f19150f0c5a5d7946
Timestamp: 1615027765 Timestamp [UCT]: 2021-03-06 10:49:25 Age [y:d:h:m:s]: 03:268:22:50:06
Block: 212616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 951561 RingCT/type: yes/0
Extra: 010ad8b17e6904c303e9161dbba16052f8b6b2135cca84e09f19150f0c5a5d79460211000000cc5ff1d2a5000000000000000000

1 output(s) for total of 121.203604656000 dcy

stealth address amount amount idx
00: 63510348601dbce72de59e01ac76cab117e1d84fb064422802e78af27ef48d3d 121.203604656000 433790 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": 212626, "vin": [ { "gen": { "height": 212616 } } ], "vout": [ { "amount": 121203604656, "target": { "key": "63510348601dbce72de59e01ac76cab117e1d84fb064422802e78af27ef48d3d" } } ], "extra": [ 1, 10, 216, 177, 126, 105, 4, 195, 3, 233, 22, 29, 187, 161, 96, 82, 248, 182, 178, 19, 92, 202, 132, 224, 159, 25, 21, 15, 12, 90, 93, 121, 70, 2, 17, 0, 0, 0, 204, 95, 241, 210, 165, 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