Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29b8893ec950e2e5bc59636b4c1534a2b71fda06e9fcb5889400690d375c894f

Tx prefix hash: 4c17bb04e7acf4c9b8190f2eb43f2540fe37cd542b8e290cb8bad9be7bf63cce
Tx public key: cf600e21bdc1e308ec0ae032bc049779ac1277aca019c173d7164a92fd995492
Timestamp: 1696236236 Timestamp [UCT]: 2023-10-02 08:43:56 Age [y:d:h:m:s]: 01:149:11:05:17
Block: 860743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367839 RingCT/type: yes/0
Extra: 01cf600e21bdc1e308ec0ae032bc049779ac1277aca019c173d7164a92fd99549202110000000575e3f0e9000000000000000000

1 output(s) for total of 0.862980874000 dcy

stealth address amount amount idx
00: 1ad2818d0ca945dda0cc8d81cede82b0f8d6d8613fbcfa823336d0c7e07a0fef 0.862980874000 1315041 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": 860753, "vin": [ { "gen": { "height": 860743 } } ], "vout": [ { "amount": 862980874, "target": { "key": "1ad2818d0ca945dda0cc8d81cede82b0f8d6d8613fbcfa823336d0c7e07a0fef" } } ], "extra": [ 1, 207, 96, 14, 33, 189, 193, 227, 8, 236, 10, 224, 50, 188, 4, 151, 121, 172, 18, 119, 172, 160, 25, 193, 115, 215, 22, 74, 146, 253, 153, 84, 146, 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