Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc8d3aad7710e6422178d3e9c346f617e0c19a25a3c60ce1b88d01c95a0d5948

Tx prefix hash: 2ece6f2aaf3cb9dc2e7a540b52812800606f2874439ce653055c1fa5016bcdb5
Tx public key: fbe7b4341021fff14361c99fb988a53c6a5538312abf3eef505a6ad29322533f
Timestamp: 1715879885 Timestamp [UCT]: 2024-05-16 17:18:05 Age [y:d:h:m:s]: 00:235:22:43:32
Block: 1023393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168876 RingCT/type: yes/0
Extra: 01fbe7b4341021fff14361c99fb988a53c6a5538312abf3eef505a6ad29322533f02110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff882e109f763cdf95210a95c052ebc3c2f707e5c8eeb326bbe92f500f3bdfd8 0.600000000000 1488340 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": 1023403, "vin": [ { "gen": { "height": 1023393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff882e109f763cdf95210a95c052ebc3c2f707e5c8eeb326bbe92f500f3bdfd8" } } ], "extra": [ 1, 251, 231, 180, 52, 16, 33, 255, 241, 67, 97, 201, 159, 185, 136, 165, 60, 106, 85, 56, 49, 42, 191, 62, 239, 80, 90, 106, 210, 147, 34, 83, 63, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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