Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0912f6222abab60f8ee2e42b66740beedc9d67dd5cde5be2a7b7e75f0da3d4ef

Tx prefix hash: 2e17da535ebedc2b86d984de6c98cb36f79305422541e9cb22861d90ad3935b2
Tx public key: 01f3eac7db9b76520358f7b687e5f035fb412df24670b017afa4f62d8dfd2617
Timestamp: 1702869243 Timestamp [UCT]: 2023-12-18 03:14:03 Age [y:d:h:m:s]: 01:328:12:56:47
Block: 915530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493667 RingCT/type: yes/0
Extra: 0101f3eac7db9b76520358f7b687e5f035fb412df24670b017afa4f62d8dfd2617021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0a47c190ab240f0c14a8a098f5b96ff09ec3c913f5e0e6476aee7931de2f450 0.600000000000 1372926 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": 915540, "vin": [ { "gen": { "height": 915530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0a47c190ab240f0c14a8a098f5b96ff09ec3c913f5e0e6476aee7931de2f450" } } ], "extra": [ 1, 1, 243, 234, 199, 219, 155, 118, 82, 3, 88, 247, 182, 135, 229, 240, 53, 251, 65, 45, 242, 70, 112, 176, 23, 175, 164, 246, 45, 141, 253, 38, 23, 2, 17, 0, 0, 0, 2, 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