Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98ffabd1dc9ea0236a7e373f028f964a895150b30ef3a27a97ae4e191d2b15ae

Tx prefix hash: 0fb22a135eecb4771fc098e3bfe4d56801819c758301c510ebb438dd4a876f19
Tx public key: f2f9d151e9756762011446438d87b18ad4e4837a665ba0efb273cc3829d5223e
Timestamp: 1730786969 Timestamp [UCT]: 2024-11-05 06:09:29 Age [y:d:h:m:s]: 00:129:13:08:14
Block: 1146892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92435 RingCT/type: yes/0
Extra: 01f2f9d151e9756762011446438d87b18ad4e4837a665ba0efb273cc3829d5223e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 971e5e1633d0f04210e0c81440bcd0a8ea03ed48e4c7a7625e2b9997c1c69c57 0.600000000000 1631583 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": 1146902, "vin": [ { "gen": { "height": 1146892 } } ], "vout": [ { "amount": 600000000, "target": { "key": "971e5e1633d0f04210e0c81440bcd0a8ea03ed48e4c7a7625e2b9997c1c69c57" } } ], "extra": [ 1, 242, 249, 209, 81, 233, 117, 103, 98, 1, 20, 70, 67, 141, 135, 177, 138, 212, 228, 131, 122, 102, 91, 160, 239, 178, 115, 204, 56, 41, 213, 34, 62, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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