Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d269148bfa94fb5f8d5c51cd8376d191e67bddf4f2d08c3fd99634128a5ba120

Tx prefix hash: 30d063355d329c4843d0ec4c2f9e414a794f246f2623c763d88c67ed987f4225
Tx public key: 8374290c89244537dbe0e1a9511883dc8f055a693386c0a15cf4e5d9e176afd6
Timestamp: 1733681163 Timestamp [UCT]: 2024-12-08 18:06:03 Age [y:d:h:m:s]: 00:109:07:35:08
Block: 1170886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77909 RingCT/type: yes/0
Extra: 018374290c89244537dbe0e1a9511883dc8f055a693386c0a15cf4e5d9e176afd60211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b617234d045070977c9610e9e1526599f7bc64765fbcb867a7650d728dbe94cb 0.600000000000 1656621 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": 1170896, "vin": [ { "gen": { "height": 1170886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b617234d045070977c9610e9e1526599f7bc64765fbcb867a7650d728dbe94cb" } } ], "extra": [ 1, 131, 116, 41, 12, 137, 36, 69, 55, 219, 224, 225, 169, 81, 24, 131, 220, 143, 5, 90, 105, 51, 134, 192, 161, 92, 244, 229, 217, 225, 118, 175, 214, 2, 17, 0, 0, 0, 4, 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