Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1d4c73cd331b4cf8b49dadf395fad723f9d29557052af1659d798ac7f28e1eb

Tx prefix hash: aa3affcc229ef4e8f6c7a797b51569f315d2c07faf7fbea3374ed51ba6b8b83a
Tx public key: 41de2fa4a50f02370affed94480b8a81605af4494c3ca44a23ff5d9a590cf1b9
Timestamp: 1721808547 Timestamp [UCT]: 2024-07-24 08:09:07 Age [y:d:h:m:s]: 00:184:05:01:25
Block: 1072545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131760 RingCT/type: yes/0
Extra: 0141de2fa4a50f02370affed94480b8a81605af4494c3ca44a23ff5d9a590cf1b9021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4314b73d4b4312990d4aeeed7b73b39fe68e0ce2b4b8a9a3aee9c9225afa98b4 0.600000000000 1545018 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": 1072555, "vin": [ { "gen": { "height": 1072545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4314b73d4b4312990d4aeeed7b73b39fe68e0ce2b4b8a9a3aee9c9225afa98b4" } } ], "extra": [ 1, 65, 222, 47, 164, 165, 15, 2, 55, 10, 255, 237, 148, 72, 11, 138, 129, 96, 90, 244, 73, 76, 60, 164, 74, 35, 255, 93, 154, 89, 12, 241, 185, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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