Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f30845f499d28b13e34ae462a5f91cbeee9e4cde6c709a2985fc406ec57c19f2

Tx prefix hash: 862fae0a87dbbfc5ec5e514de6e87e6a26c89ed23f61a298290ddd524948f15c
Tx public key: 2f46d09ceec474c055ef404fc1fca6677db04ed40a4b5970b0bb303cde72a75e
Timestamp: 1695312801 Timestamp [UCT]: 2023-09-21 16:13:21 Age [y:d:h:m:s]: 01:269:14:00:36
Block: 853080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453682 RingCT/type: yes/0
Extra: 012f46d09ceec474c055ef404fc1fca6677db04ed40a4b5970b0bb303cde72a75e0211000000018bcdc0ce000000000000000000

1 output(s) for total of 0.914938456000 dcy

stealth address amount amount idx
00: 3c8068f001d55003c53dc11a97618ca67e029eb4a09209e9b2f404605ce79642 0.914938456000 1306956 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": 853090, "vin": [ { "gen": { "height": 853080 } } ], "vout": [ { "amount": 914938456, "target": { "key": "3c8068f001d55003c53dc11a97618ca67e029eb4a09209e9b2f404605ce79642" } } ], "extra": [ 1, 47, 70, 208, 156, 238, 196, 116, 192, 85, 239, 64, 79, 193, 252, 166, 103, 125, 176, 78, 212, 10, 75, 89, 112, 176, 187, 48, 60, 222, 114, 167, 94, 2, 17, 0, 0, 0, 1, 139, 205, 192, 206, 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