Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557318b68222bd239f2f60f6a1c4d6401072035e99b045a494d8b63be878215f

Tx prefix hash: 6e103fa3eef195c0c9a95b1d5eeb2a6f2cb2e27cd81de13e4051549a6e045570
Tx public key: c70696e8216a7cf462cff08e8b09bda9f9f1c0481a7493cf0ce124076bb6d3bc
Timestamp: 1719119757 Timestamp [UCT]: 2024-06-23 05:15:57 Age [y:d:h:m:s]: 00:291:00:56:40
Block: 1050242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207987 RingCT/type: yes/0
Extra: 01c70696e8216a7cf462cff08e8b09bda9f9f1c0481a7493cf0ce124076bb6d3bc02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b65491efcfb74cf96a703b686bac041237a0701d217cbfbe36f75e6ea481dd1 0.600000000000 1520403 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": 1050252, "vin": [ { "gen": { "height": 1050242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b65491efcfb74cf96a703b686bac041237a0701d217cbfbe36f75e6ea481dd1" } } ], "extra": [ 1, 199, 6, 150, 232, 33, 106, 124, 244, 98, 207, 240, 142, 139, 9, 189, 169, 249, 241, 192, 72, 26, 116, 147, 207, 12, 225, 36, 7, 107, 182, 211, 188, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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