Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 785fba866716867a2dd4118ab51cc17ae2f5df0f36d7265b04ca3b4e313537bf

Tx prefix hash: 96bf299b069df5d8ee21f313dc59c448b6b83222fd58959fe0a2547b4dc02f95
Tx public key: c28dad2b4e0ca56bd51ba3d7ed9bb46fb0490bb30f8017bcd0777db38bad386c
Timestamp: 1706871419 Timestamp [UCT]: 2024-02-02 10:56:59 Age [y:d:h:m:s]: 01:061:15:07:35
Block: 948708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305097 RingCT/type: yes/0
Extra: 01c28dad2b4e0ca56bd51ba3d7ed9bb46fb0490bb30f8017bcd0777db38bad386c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e3ea44b8b93b77e675d7b1d16a46cfc44c6717903b3ef74f1b380aeb2856a3a 0.600000000000 1407170 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": 948718, "vin": [ { "gen": { "height": 948708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e3ea44b8b93b77e675d7b1d16a46cfc44c6717903b3ef74f1b380aeb2856a3a" } } ], "extra": [ 1, 194, 141, 173, 43, 78, 12, 165, 107, 213, 27, 163, 215, 237, 155, 180, 111, 176, 73, 11, 179, 15, 128, 23, 188, 208, 119, 125, 179, 139, 173, 56, 108, 2, 17, 0, 0, 0, 2, 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