Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbaa72f807fe86678146ba80414691715db746c55a6b2e734ddbaa7118d94860

Tx prefix hash: 0171fb026cc4d27bc8bb2cb20c7b4d8a2500d96f0288658e40cb1c1225059d22
Tx public key: e8c1ffb8f6f9c1049c87a8a103c211787c37ab8c618a5dbabbfd32d7e5b16f3c
Timestamp: 1730796483 Timestamp [UCT]: 2024-11-05 08:48:03 Age [y:d:h:m:s]: 00:143:21:22:49
Block: 1146978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102666 RingCT/type: yes/0
Extra: 01e8c1ffb8f6f9c1049c87a8a103c211787c37ab8c618a5dbabbfd32d7e5b16f3c021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c10f6f28a1fadaa334f246c31d6e7d4f2a748f0a582355fa7a9c872b527da835 0.600000000000 1631671 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": 1146988, "vin": [ { "gen": { "height": 1146978 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c10f6f28a1fadaa334f246c31d6e7d4f2a748f0a582355fa7a9c872b527da835" } } ], "extra": [ 1, 232, 193, 255, 184, 246, 249, 193, 4, 156, 135, 168, 161, 3, 194, 17, 120, 124, 55, 171, 140, 97, 138, 93, 186, 187, 253, 50, 215, 229, 177, 111, 60, 2, 17, 0, 0, 0, 7, 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