Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b90dddc0bf080bfa19ae1f0d6118dc79f9680620c6f8ed0001843769e2ab1d20

Tx prefix hash: 5e991e488f586c7a2e2675c2e080ab4ec8bf5601c1bc9555e3d2fc7b769fbd79
Tx public key: ca6aa64a094602b3f370b9c73ecef7bc89140f501c8262a47713e44fbbdf9b37
Timestamp: 1658961971 Timestamp [UCT]: 2022-07-27 22:46:11 Age [y:d:h:m:s]: 03:096:11:14:44
Block: 553137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 848724 RingCT/type: yes/0
Extra: 01ca6aa64a094602b3f370b9c73ecef7bc89140f501c8262a47713e44fbbdf9b37021100000005aac913b7000000000000000000

1 output(s) for total of 9.020438057000 dcy

stealth address amount amount idx
00: 34262f5fd902baa8085a79383e355d1a5dc90d3e0e121e3d0bb0280ffd9bf37a 9.020438057000 984909 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": 553147, "vin": [ { "gen": { "height": 553137 } } ], "vout": [ { "amount": 9020438057, "target": { "key": "34262f5fd902baa8085a79383e355d1a5dc90d3e0e121e3d0bb0280ffd9bf37a" } } ], "extra": [ 1, 202, 106, 166, 74, 9, 70, 2, 179, 243, 112, 185, 199, 62, 206, 247, 188, 137, 20, 15, 80, 28, 130, 98, 164, 119, 19, 228, 79, 187, 223, 155, 55, 2, 17, 0, 0, 0, 5, 170, 201, 19, 183, 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