Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb70773b1bfa146d72c5a99b1401450c539cb032833effcbe4cc68998bf8882f

Tx prefix hash: ddd4e98b423d02f7e676ed1404351f3b5d9607c18b0f1dddeefecc84840dacb3
Tx public key: 72aee78451a211b05333053220276a5f1c57197be72b1ae0e0e967942f57b8d6
Timestamp: 1736017208 Timestamp [UCT]: 2025-01-04 19:00:08 Age [y:d:h:m:s]: 00:136:15:04:34
Block: 1190214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97465 RingCT/type: yes/0
Extra: 0172aee78451a211b05333053220276a5f1c57197be72b1ae0e0e967942f57b8d602110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c7e2bff2143169ebc7d8d0c44f397b94aec42d4b4852c9085263cbcc1d4ea01 0.600000000000 1676729 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": 1190224, "vin": [ { "gen": { "height": 1190214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c7e2bff2143169ebc7d8d0c44f397b94aec42d4b4852c9085263cbcc1d4ea01" } } ], "extra": [ 1, 114, 174, 231, 132, 81, 162, 17, 176, 83, 51, 5, 50, 32, 39, 106, 95, 28, 87, 25, 123, 231, 43, 26, 224, 224, 233, 103, 148, 47, 87, 184, 214, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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