Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baeff9a9628742fd1f15e005e4151cd3903e371621d94b3a13be2c854fdc974f

Tx prefix hash: 0030783303ce3cc0dfc6ef82bb2d35aaec5a32349c09da6877f7d39c0dde0ffc
Tx public key: 66402c72d21a66638efa8ba3e0330f24e2ec4f1c386d3f9ca1d42828b3481516
Timestamp: 1714034184 Timestamp [UCT]: 2024-04-25 08:36:24 Age [y:d:h:m:s]: 01:001:08:29:42
Block: 1008092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261918 RingCT/type: yes/0
Extra: 0166402c72d21a66638efa8ba3e0330f24e2ec4f1c386d3f9ca1d42828b348151602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d7b8e15f543c2fa4d0c6175621cac75a07f3a0047d1af691eff5c12e37a348d 0.600000000000 1469558 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": 1008102, "vin": [ { "gen": { "height": 1008092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d7b8e15f543c2fa4d0c6175621cac75a07f3a0047d1af691eff5c12e37a348d" } } ], "extra": [ 1, 102, 64, 44, 114, 210, 26, 102, 99, 142, 250, 139, 163, 224, 51, 15, 36, 226, 236, 79, 28, 56, 109, 63, 156, 161, 212, 40, 40, 179, 72, 21, 22, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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