Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb487cb7e8f2ecde1a6b34d780abcb37038076076c5b2d98c4c11161776d3575

Tx prefix hash: ee7ac7767dd5f188d72322a88c909ef3a985c4a651118f6f9826d9a030efbff5
Tx public key: 63a6bd0bddcacfc0d33c40f8ebb2143285231cd5d91c84146baeb1ca502ede9a
Timestamp: 1648841657 Timestamp [UCT]: 2022-04-01 19:34:17 Age [y:d:h:m:s]: 02:311:20:05:29
Block: 471128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 742329 RingCT/type: yes/0
Extra: 0163a6bd0bddcacfc0d33c40f8ebb2143285231cd5d91c84146baeb1ca502ede9a021100000001a272b9cb000000000000000000

1 output(s) for total of 16.863884119000 dcy

stealth address amount amount idx
00: f79d956d37e680997d89b7dddbc8fb8de069b60ac0a62dcc7136da430a00e75c 16.863884119000 890408 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": 471138, "vin": [ { "gen": { "height": 471128 } } ], "vout": [ { "amount": 16863884119, "target": { "key": "f79d956d37e680997d89b7dddbc8fb8de069b60ac0a62dcc7136da430a00e75c" } } ], "extra": [ 1, 99, 166, 189, 11, 221, 202, 207, 192, 211, 60, 64, 248, 235, 178, 20, 50, 133, 35, 28, 213, 217, 28, 132, 20, 107, 174, 177, 202, 80, 46, 222, 154, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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