Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f07a7cf8169af95872dcfb20b4c09e7e33f2782f5d8336f738c4db13bd007656

Tx prefix hash: 5f67fda95d35f17deafeddcbd43f316450e3d04dbcf0e412039f63bd284353ff
Tx public key: b48113194a134d6f525c0c64ab6d13da623a6b6e788aea421ee5cef0326a1033
Timestamp: 1709716656 Timestamp [UCT]: 2024-03-06 09:17:36 Age [y:d:h:m:s]: 01:099:15:33:02
Block: 972315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332175 RingCT/type: yes/0
Extra: 01b48113194a134d6f525c0c64ab6d13da623a6b6e788aea421ee5cef0326a10330211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22c3eaed8bcf389e362207d45ce5b3f1ee77e5f6d942ee3c790ae72210a72e72 0.600000000000 1432224 of 15

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": 972325, "vin": [ { "gen": { "height": 972315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22c3eaed8bcf389e362207d45ce5b3f1ee77e5f6d942ee3c790ae72210a72e72" } } ], "extra": [ 1, 180, 129, 19, 25, 74, 19, 77, 111, 82, 92, 12, 100, 171, 109, 19, 218, 98, 58, 107, 110, 120, 138, 234, 66, 30, 229, 206, 240, 50, 106, 16, 51, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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