Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c72e3d9990d5d89939b770a902b8b543b6c776e9ad84f69be2f170683abce8d2

Tx prefix hash: 7790fd3df3402ba6ffb0e3b2db35c3c5b7009233e71c41a5087d583cfc2203df
Tx public key: 4be8634ff1f5cad5034bdea6b08aab4042a4bd458fee0ff65fb880907812bce9
Timestamp: 1716662750 Timestamp [UCT]: 2024-05-25 18:45:50 Age [y:d:h:m:s]: 01:167:04:58:10
Block: 1029896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378086 RingCT/type: yes/0
Extra: 014be8634ff1f5cad5034bdea6b08aab4042a4bd458fee0ff65fb880907812bce902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b961460404e16a39ddbc692ff0fc57d6eb1bf4f08be2102f50d6f6ea4626dfe3 0.600000000000 1498111 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": 1029906, "vin": [ { "gen": { "height": 1029896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b961460404e16a39ddbc692ff0fc57d6eb1bf4f08be2102f50d6f6ea4626dfe3" } } ], "extra": [ 1, 75, 232, 99, 79, 241, 245, 202, 213, 3, 75, 222, 166, 176, 138, 171, 64, 66, 164, 189, 69, 143, 238, 15, 246, 95, 184, 128, 144, 120, 18, 188, 233, 2, 17, 0, 0, 0, 2, 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