Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e46d8514bfac20e79a0a1ae6b1df34804af005451ff5704c73ce1025e10c41a2

Tx prefix hash: 870e4c159078dee6e291b00380f3b3a9ffdc0ae4b02ec1ad5b39edc61e8beaff
Tx public key: 5f6b6c81271ed797af5fb9839093961eeb560e10c4e905c7890b7f675ca97ef2
Timestamp: 1672863250 Timestamp [UCT]: 2023-01-04 20:14:10 Age [y:d:h:m:s]: 02:090:14:33:38
Block: 667641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586431 RingCT/type: yes/0
Extra: 015f6b6c81271ed797af5fb9839093961eeb560e10c4e905c7890b7f675ca97ef202110000000575e3f0e9000000000000000000

1 output(s) for total of 3.765547902000 dcy

stealth address amount amount idx
00: 4a16e052b3be17d4d044bf3cd78d0c73dc7ca77fdb34226a3d03ef782d9da068 3.765547902000 1108856 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": 667651, "vin": [ { "gen": { "height": 667641 } } ], "vout": [ { "amount": 3765547902, "target": { "key": "4a16e052b3be17d4d044bf3cd78d0c73dc7ca77fdb34226a3d03ef782d9da068" } } ], "extra": [ 1, 95, 107, 108, 129, 39, 30, 215, 151, 175, 95, 185, 131, 144, 147, 150, 30, 235, 86, 14, 16, 196, 233, 5, 199, 137, 11, 127, 103, 92, 169, 126, 242, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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