Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbb87416d60f51f50a50a7678117e79f25b6cdfda277b78caf603964c8d64481

Tx prefix hash: e007b8bb7144acd407463c0fc2cd3c9ec0c85b2fc5911394b8dd08cf8f55d2b3
Tx public key: af44dcbfb9d4eb7bb043da8969f00dd9c29ae18d866d1388bcc9ba02a5e80e73
Timestamp: 1704623669 Timestamp [UCT]: 2024-01-07 10:34:29 Age [y:d:h:m:s]: 01:123:13:37:42
Block: 930061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349448 RingCT/type: yes/0
Extra: 01af44dcbfb9d4eb7bb043da8969f00dd9c29ae18d866d1388bcc9ba02a5e80e730211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 546a5b2d893e2bb890e7863fe7b5ca972d5144141db3927152b08a885063161d 0.600000000000 1387939 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": 930071, "vin": [ { "gen": { "height": 930061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "546a5b2d893e2bb890e7863fe7b5ca972d5144141db3927152b08a885063161d" } } ], "extra": [ 1, 175, 68, 220, 191, 185, 212, 235, 123, 176, 67, 218, 137, 105, 240, 13, 217, 194, 154, 225, 141, 134, 109, 19, 136, 188, 201, 186, 2, 165, 232, 14, 115, 2, 17, 0, 0, 0, 1, 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