Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f191032bcd307fb715674dc62308d63a202700665596363c5dd1aa88f867ea1

Tx prefix hash: 9f121b1f19557632bc6386bcb79d39c51c6fac54c9c6394871a574680ef8efb4
Tx public key: 922da78ad9c732be63466b7fee245945d7f1aef00c6308162eb07481a832ba90
Timestamp: 1574724307 Timestamp [UCT]: 2019-11-25 23:25:07 Age [y:d:h:m:s]: 05:100:13:47:57
Block: 17505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1214474 RingCT/type: yes/0
Extra: 01922da78ad9c732be63466b7fee245945d7f1aef00c6308162eb07481a832ba900211000000040b4dd45a000000000000000000

1 output(s) for total of 537.031238451000 dcy

stealth address amount amount idx
00: 30949cb0bea472a614fdd8db1893b5d62ae5e1caaad26f0e4859d29aea919e04 537.031238451000 25536 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": 17515, "vin": [ { "gen": { "height": 17505 } } ], "vout": [ { "amount": 537031238451, "target": { "key": "30949cb0bea472a614fdd8db1893b5d62ae5e1caaad26f0e4859d29aea919e04" } } ], "extra": [ 1, 146, 45, 167, 138, 217, 199, 50, 190, 99, 70, 107, 127, 238, 36, 89, 69, 215, 241, 174, 240, 12, 99, 8, 22, 46, 176, 116, 129, 168, 50, 186, 144, 2, 17, 0, 0, 0, 4, 11, 77, 212, 90, 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