Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdd1efda5f46a1af5c3daeb353c3297a4b3aa603cdaf0f3d1ae12a11083ea39b

Tx prefix hash: c4245f933c49da085c39a074b4ad97c582ba2c167f8645254c439612b55089cf
Tx public key: e26b87903b114d7572f30866c5e940fee61ac692c51654ef10d3f306d60f2a59
Timestamp: 1709403209 Timestamp [UCT]: 2024-03-02 18:13:29 Age [y:d:h:m:s]: 01:072:01:54:59
Block: 969714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312537 RingCT/type: yes/0
Extra: 01e26b87903b114d7572f30866c5e940fee61ac692c51654ef10d3f306d60f2a5902110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f27bafa65911ec6abf3c870e27c363f15f3901cd026f46da0de58499044f3881 0.600000000000 1429553 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": 969724, "vin": [ { "gen": { "height": 969714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f27bafa65911ec6abf3c870e27c363f15f3901cd026f46da0de58499044f3881" } } ], "extra": [ 1, 226, 107, 135, 144, 59, 17, 77, 117, 114, 243, 8, 102, 197, 233, 64, 254, 230, 26, 198, 146, 197, 22, 84, 239, 16, 211, 243, 6, 214, 15, 42, 89, 2, 17, 0, 0, 0, 13, 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