Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56312559f8a891e92188055083548d6c005bfe3a0f32cbfca105a6924776081b

Tx prefix hash: a0793c91735821f1741e6280e243234057d56c814f89c0eec2946c8c4b4b7f20
Tx public key: f9cb27638f3cd7d60d07ab99d9f6615c27a09aa2f16af60f5b2739f6ccd8d49c
Timestamp: 1696675159 Timestamp [UCT]: 2023-10-07 10:39:19 Age [y:d:h:m:s]: 01:166:21:44:10
Block: 864380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380326 RingCT/type: yes/0
Extra: 01f9cb27638f3cd7d60d07ab99d9f6615c27a09aa2f16af60f5b2739f6ccd8d49c02110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.839363876000 dcy

stealth address amount amount idx
00: 2b4f1974d085ff13d5f66ed234667d52f16558a8b16a6a22d35e9e231b8ba3f2 0.839363876000 1318894 of 0

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": 864390, "vin": [ { "gen": { "height": 864380 } } ], "vout": [ { "amount": 839363876, "target": { "key": "2b4f1974d085ff13d5f66ed234667d52f16558a8b16a6a22d35e9e231b8ba3f2" } } ], "extra": [ 1, 249, 203, 39, 99, 143, 60, 215, 214, 13, 7, 171, 153, 217, 246, 97, 92, 39, 160, 154, 162, 241, 106, 246, 15, 91, 39, 57, 246, 204, 216, 212, 156, 2, 17, 0, 0, 0, 12, 230, 210, 127, 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