Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85d315951f9b01a3c7d655b11c20db2cd52abf90ffa39dcbe560febdf084f730

Tx prefix hash: 0c08e9b080020483a79a68baf3b9f05def7053f4038948cbf7535333f93ba63c
Tx public key: d11e757d7e236c4039702d5177356903cd1ecddd1915a9ed65a37c7de9fb5f91
Timestamp: 1706591136 Timestamp [UCT]: 2024-01-30 05:05:36 Age [y:d:h:m:s]: 01:128:22:31:25
Block: 946369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353273 RingCT/type: yes/0
Extra: 01d11e757d7e236c4039702d5177356903cd1ecddd1915a9ed65a37c7de9fb5f910211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d83a635d7655dc2b2bb586841ed719e6d16f2b41c15d933232b4e068a95c31b0 0.600000000000 1404701 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": 946379, "vin": [ { "gen": { "height": 946369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d83a635d7655dc2b2bb586841ed719e6d16f2b41c15d933232b4e068a95c31b0" } } ], "extra": [ 1, 209, 30, 117, 125, 126, 35, 108, 64, 57, 112, 45, 81, 119, 53, 105, 3, 205, 30, 205, 221, 25, 21, 169, 237, 101, 163, 124, 125, 233, 251, 95, 145, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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