Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34099b910718117775ad6ae67ed89a0371b8bad9527bb8c0d6293b8bf28d9613

Tx prefix hash: d19d7733db3b06ba87adbcc7398b7d25fb541996d8a649a10b8b6f55a39f9ca5
Tx public key: 3146153e5b3f229dee241c0b698c1c09efec612766d4755f9fb32c2c09eb2aae
Timestamp: 1703605520 Timestamp [UCT]: 2023-12-26 15:45:20 Age [y:d:h:m:s]: 01:346:11:03:24
Block: 921636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506485 RingCT/type: yes/0
Extra: 013146153e5b3f229dee241c0b698c1c09efec612766d4755f9fb32c2c09eb2aae02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ad32af92dd408eb02f5e84c9211bc9f49b0f9f72ccd188067b59d64fe4eb48e 0.600000000000 1379326 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": 921646, "vin": [ { "gen": { "height": 921636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ad32af92dd408eb02f5e84c9211bc9f49b0f9f72ccd188067b59d64fe4eb48e" } } ], "extra": [ 1, 49, 70, 21, 62, 91, 63, 34, 157, 238, 36, 28, 11, 105, 140, 28, 9, 239, 236, 97, 39, 102, 212, 117, 95, 159, 179, 44, 44, 9, 235, 42, 174, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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