Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f06e1237137395f4035d9501bc584fa160f6d82f4463f64ccefa477d4759e0

Tx prefix hash: d108a60e4622e7db79c9f55c870cf7c02162fd44a9a5f1cc19e2cf5a465afc67
Tx public key: b09ecaeb8243a49e35d1ea52e9e22923fe49e8c7a2dcf525f4164a4704c62097
Timestamp: 1707811332 Timestamp [UCT]: 2024-02-13 08:02:12 Age [y:d:h:m:s]: 01:013:16:18:10
Block: 956500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270782 RingCT/type: yes/0
Extra: 01b09ecaeb8243a49e35d1ea52e9e22923fe49e8c7a2dcf525f4164a4704c620970211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fa8e1d4352f2109d1673fda7f7fae84fec302ab7a684dc7dd57cf73be35d4e8 0.600000000000 1415808 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": 956510, "vin": [ { "gen": { "height": 956500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fa8e1d4352f2109d1673fda7f7fae84fec302ab7a684dc7dd57cf73be35d4e8" } } ], "extra": [ 1, 176, 158, 202, 235, 130, 67, 164, 158, 53, 209, 234, 82, 233, 226, 41, 35, 254, 73, 232, 199, 162, 220, 245, 37, 244, 22, 74, 71, 4, 198, 32, 151, 2, 17, 0, 0, 0, 8, 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