Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19cac751fa61036c160d1c71443c62b1f4fe87f0140f42dd21fdd28491d33cfc

Tx prefix hash: c2704b01d6f159854deb1365f94f2b4473005f3c05231b3a48f573a6e2122576
Tx public key: 8d596abd22ae48759b81fc1fed95f23f433d6a4d082be86f8056c8d56b14320d
Timestamp: 1727916015 Timestamp [UCT]: 2024-10-03 00:40:15 Age [y:d:h:m:s]: 00:171:06:24:44
Block: 1123186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122193 RingCT/type: yes/0
Extra: 018d596abd22ae48759b81fc1fed95f23f433d6a4d082be86f8056c8d56b14320d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ddaeb3e7a7371fdab5a8c0dcd61e6ddae5da28aa35fd71a1c7dfe880f945809 0.600000000000 1605719 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": 1123196, "vin": [ { "gen": { "height": 1123186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ddaeb3e7a7371fdab5a8c0dcd61e6ddae5da28aa35fd71a1c7dfe880f945809" } } ], "extra": [ 1, 141, 89, 106, 189, 34, 174, 72, 117, 155, 129, 252, 31, 237, 149, 242, 63, 67, 61, 106, 77, 8, 43, 232, 111, 128, 86, 200, 213, 107, 20, 50, 13, 2, 17, 0, 0, 0, 3, 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