Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c72410dce424200051d68a41a02e78e6391218ee8c3773b94efc185aeb5a236

Tx prefix hash: 7e4b9afddf9ea6de717269b7f1fce40642cab0e2181a5521a99af4e3edc0f496
Tx public key: 20d5345363dc866f6b65e3a5aaa6b47a4f1300f32ed4e3ef73bc4f8890d25fa1
Timestamp: 1740005549 Timestamp [UCT]: 2025-02-19 22:52:29 Age [y:d:h:m:s]: 00:230:21:05:39
Block: 1222939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162726 RingCT/type: yes/0
Extra: 0120d5345363dc866f6b65e3a5aaa6b47a4f1300f32ed4e3ef73bc4f8890d25fa1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 112b4190e5c035c78d81130d2e431bc35071c36a41b6323fd541af7fe14e5b6a 0.600000000000 1709794 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": 1222949, "vin": [ { "gen": { "height": 1222939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "112b4190e5c035c78d81130d2e431bc35071c36a41b6323fd541af7fe14e5b6a" } } ], "extra": [ 1, 32, 213, 52, 83, 99, 220, 134, 111, 107, 101, 227, 165, 170, 166, 180, 122, 79, 19, 0, 243, 46, 212, 227, 239, 115, 188, 79, 136, 144, 210, 95, 161, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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