Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbd10428dfa06e8f6b4d3be896862b9520d4608e52727079b70c4c1acc583856

Tx prefix hash: 658cd7f1eb8398210fb232721f0d1fe7e776d27cc815dc06cff75afb6ed7deb6
Tx public key: 5bb444cca12e750e5bea6e78d5debe302d8dc7052f63c286ae0deddaa6e61927
Timestamp: 1703551204 Timestamp [UCT]: 2023-12-26 00:40:04 Age [y:d:h:m:s]: 01:319:21:24:23
Block: 921187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487470 RingCT/type: yes/0
Extra: 015bb444cca12e750e5bea6e78d5debe302d8dc7052f63c286ae0deddaa6e619270211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17edf5fed0e57db67ed912d1c48b60fe8c8cf36d9f8da941375562a8a15cb469 0.600000000000 1378873 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": 921197, "vin": [ { "gen": { "height": 921187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17edf5fed0e57db67ed912d1c48b60fe8c8cf36d9f8da941375562a8a15cb469" } } ], "extra": [ 1, 91, 180, 68, 204, 161, 46, 117, 14, 91, 234, 110, 120, 213, 222, 190, 48, 45, 141, 199, 5, 47, 99, 194, 134, 174, 13, 237, 218, 166, 230, 25, 39, 2, 17, 0, 0, 0, 3, 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