Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0782f82f93aa8bd5c84b677de782273c7e0587e68169b23f647f3a9bc0a5429e

Tx prefix hash: 3862ec4a237f8fe01f56c5b966ff3b62e3eeeaf3c1d68eba7694113fa500af18
Tx public key: 2c91da1ec7f1ecfeb566067d9db7c2ec8502b41fabde8c48fb6012ef044ee0dd
Timestamp: 1724550769 Timestamp [UCT]: 2024-08-25 01:52:49 Age [y:d:h:m:s]: 00:300:21:15:13
Block: 1095312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214743 RingCT/type: yes/0
Extra: 012c91da1ec7f1ecfeb566067d9db7c2ec8502b41fabde8c48fb6012ef044ee0dd021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a854cbf53bbb5866a554e7e5f5a6b1d18929057e329e7384bb7e88d86dfc675 0.600000000000 1570473 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": 1095322, "vin": [ { "gen": { "height": 1095312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a854cbf53bbb5866a554e7e5f5a6b1d18929057e329e7384bb7e88d86dfc675" } } ], "extra": [ 1, 44, 145, 218, 30, 199, 241, 236, 254, 181, 102, 6, 125, 157, 183, 194, 236, 133, 2, 180, 31, 171, 222, 140, 72, 251, 96, 18, 239, 4, 78, 224, 221, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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