Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc41316943c0f1b23e884467af96d7ed3c8100ded4f7444b6c7f39bed6813f36

Tx prefix hash: 395577f32fde8d7c9da26b0c37d0e134ac32e35da94389aeff437204a707fbc2
Tx public key: c1d18a8044cc485759aa78b51d977f625b5a7fe4e74da01814fddaa05b1f2a70
Timestamp: 1702724677 Timestamp [UCT]: 2023-12-16 11:04:37 Age [y:d:h:m:s]: 01:135:06:32:01
Block: 914333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357835 RingCT/type: yes/0
Extra: 01c1d18a8044cc485759aa78b51d977f625b5a7fe4e74da01814fddaa05b1f2a70021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a19984f31f60b5c37cdce2dd5fddc466bd370bf4bd7ee788576ee3b02b86fd6b 0.600000000000 1371647 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": 914343, "vin": [ { "gen": { "height": 914333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a19984f31f60b5c37cdce2dd5fddc466bd370bf4bd7ee788576ee3b02b86fd6b" } } ], "extra": [ 1, 193, 209, 138, 128, 68, 204, 72, 87, 89, 170, 120, 181, 29, 151, 127, 98, 91, 90, 127, 228, 231, 77, 160, 24, 20, 253, 218, 160, 91, 31, 42, 112, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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