Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0794ad0e33081e06fbf83ec9a4e355b1e75d6da33c76475ec3a46c87dc19d062

Tx prefix hash: cc808d626f4d5cff7b54c0b528139e4905b76e066fb910ea8bb0bb656fbc1508
Tx public key: c7d27b51a528feb8c9e79f250aba1500c954d14e96da2d6df2260bdf1a60ae9a
Timestamp: 1577484594 Timestamp [UCT]: 2019-12-27 22:09:54 Age [y:d:h:m:s]: 05:006:18:27:45
Block: 33105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154888 RingCT/type: yes/0
Extra: 01c7d27b51a528feb8c9e79f250aba1500c954d14e96da2d6df2260bdf1a60ae9a0211000000114ac5aa02000000000000000000

1 output(s) for total of 476.771459971000 dcy

stealth address amount amount idx
00: b2e9b54c2262d0331c5aefd47ede1bef36b0d33c9ccb2e1cf00cdbda0abb8111 476.771459971000 55287 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": 33115, "vin": [ { "gen": { "height": 33105 } } ], "vout": [ { "amount": 476771459971, "target": { "key": "b2e9b54c2262d0331c5aefd47ede1bef36b0d33c9ccb2e1cf00cdbda0abb8111" } } ], "extra": [ 1, 199, 210, 123, 81, 165, 40, 254, 184, 201, 231, 159, 37, 10, 186, 21, 0, 201, 84, 209, 78, 150, 218, 45, 109, 242, 38, 11, 223, 26, 96, 174, 154, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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