Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36145d5c0db9f05e457c6cdf59bd02b39456d4877b71c7ca1eb4230073d6d60f

Tx prefix hash: cb321e85b01fd624704e770260c4b19285e5675a9eeea0be7a9356bab3b0da46
Tx public key: b2e3e5143ada28a791e066f6dccb79160b9ce121021f6d6cd15e08fb1722200e
Timestamp: 1730814285 Timestamp [UCT]: 2024-11-05 13:44:45 Age [y:d:h:m:s]: 00:144:18:26:04
Block: 1147120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103295 RingCT/type: yes/0
Extra: 01b2e3e5143ada28a791e066f6dccb79160b9ce121021f6d6cd15e08fb1722200e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faf8902884bf9eb9f21c55e12ff63ad0e59cf5271cb77ac95761b1ae803bf81a 0.600000000000 1631813 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": 1147130, "vin": [ { "gen": { "height": 1147120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faf8902884bf9eb9f21c55e12ff63ad0e59cf5271cb77ac95761b1ae803bf81a" } } ], "extra": [ 1, 178, 227, 229, 20, 58, 218, 40, 167, 145, 224, 102, 246, 220, 203, 121, 22, 11, 156, 225, 33, 2, 31, 109, 108, 209, 94, 8, 251, 23, 34, 32, 14, 2, 17, 0, 0, 0, 1, 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