Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 147d82b9f6066c3c35c6c82e2d50c93ace272290f5767df7628b8b43947278b8

Tx prefix hash: 4b04acf671149efaec6017070e4f3c9e86295e8aa780a49ef53aee87788f488c
Tx public key: f86e4e9106d4c904641e39edcc0546501e11f0a46a0ccde760423bdf47e07357
Timestamp: 1703037293 Timestamp [UCT]: 2023-12-20 01:54:53 Age [y:d:h:m:s]: 01:119:03:33:52
Block: 916926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346277 RingCT/type: yes/0
Extra: 01f86e4e9106d4c904641e39edcc0546501e11f0a46a0ccde760423bdf47e07357021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f488319ef243b7827c07334f5e6ff0b8b5544dc17929bdeab4b2bc5f22029f1c 0.600000000000 1374488 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": 916936, "vin": [ { "gen": { "height": 916926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f488319ef243b7827c07334f5e6ff0b8b5544dc17929bdeab4b2bc5f22029f1c" } } ], "extra": [ 1, 248, 110, 78, 145, 6, 212, 201, 4, 100, 30, 57, 237, 204, 5, 70, 80, 30, 17, 240, 164, 106, 12, 205, 231, 96, 66, 59, 223, 71, 224, 115, 87, 2, 17, 0, 0, 0, 5, 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