Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb417c44cae1c55a78540d7b1d11f38c1821467ef5bb36e528934c54eabc50c9

Tx prefix hash: 42dcf9d48e9bb5012cf5dc01323ddbc66c78b689d12978444f4a7042e2c11c16
Tx public key: 030381409aeb7bd449b7bb56f0ee02ea1f5d8fe6dd5f6e204a97849e3bc4b0cc
Timestamp: 1578027068 Timestamp [UCT]: 2020-01-03 04:51:08 Age [y:d:h:m:s]: 05:058:00:57:37
Block: 37555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1191328 RingCT/type: yes/0
Extra: 01030381409aeb7bd449b7bb56f0ee02ea1f5d8fe6dd5f6e204a97849e3bc4b0cc021100000010d81c26c0000000000000000000

1 output(s) for total of 460.856318711000 dcy

stealth address amount amount idx
00: 7603d619d1e4bdbaf37b9459619b2260cdc8ec9ae40637fff6d3ec86a3cc6c67 460.856318711000 63809 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": 37565, "vin": [ { "gen": { "height": 37555 } } ], "vout": [ { "amount": 460856318711, "target": { "key": "7603d619d1e4bdbaf37b9459619b2260cdc8ec9ae40637fff6d3ec86a3cc6c67" } } ], "extra": [ 1, 3, 3, 129, 64, 154, 235, 123, 212, 73, 183, 187, 86, 240, 238, 2, 234, 31, 93, 143, 230, 221, 95, 110, 32, 74, 151, 132, 158, 59, 196, 176, 204, 2, 17, 0, 0, 0, 16, 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