Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdfa9750b02d2ea8b6086f387605d7aa97faf6c36888e15cdd972876101d980c

Tx prefix hash: b7bf4346d8fb905ef5e1a2b675a6fededdcf1b2777eaa0011facc8044e8dee86
Tx public key: 86b936bc4da3afa9d9a2d65b346004c46f8eb10d067d6c489b3fc264402bedd2
Timestamp: 1578237965 Timestamp [UCT]: 2020-01-05 15:26:05 Age [y:d:h:m:s]: 04:363:04:37:57
Block: 39287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148805 RingCT/type: yes/0
Extra: 0186b936bc4da3afa9d9a2d65b346004c46f8eb10d067d6c489b3fc264402bedd20211000000054ac5aa02000000000000000000

1 output(s) for total of 454.806548133000 dcy

stealth address amount amount idx
00: 0b0e1223795c59913bd5d1be50829658e7d9f08f913f3b75d4849be3b2d98d34 454.806548133000 67621 of 0

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": 39297, "vin": [ { "gen": { "height": 39287 } } ], "vout": [ { "amount": 454806548133, "target": { "key": "0b0e1223795c59913bd5d1be50829658e7d9f08f913f3b75d4849be3b2d98d34" } } ], "extra": [ 1, 134, 185, 54, 188, 77, 163, 175, 169, 217, 162, 214, 91, 52, 96, 4, 196, 111, 142, 177, 13, 6, 125, 108, 72, 155, 63, 194, 100, 64, 43, 237, 210, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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