Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4caf2566f0bf9d6ef99abd92f3e52f74c9456bf47f7f6837c297215a759cafd8

Tx prefix hash: 19d9e2c10730a32c2ab63ce7bcaec67a12bb3e2720ba51b76407a466c37b1f4a
Tx public key: 218588b5de7b9026385505c10d6d6fbeae63e3e174b8432293d1a9372c7ef3ea
Timestamp: 1708753367 Timestamp [UCT]: 2024-02-24 05:42:47 Age [y:d:h:m:s]: 01:040:08:48:02
Block: 964319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289869 RingCT/type: yes/0
Extra: 01218588b5de7b9026385505c10d6d6fbeae63e3e174b8432293d1a9372c7ef3ea02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d56e9f8d9bd0568c9db63c900a8c8448727af5c58fb043cfeb498f318a90b862 0.600000000000 1424050 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": 964329, "vin": [ { "gen": { "height": 964319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d56e9f8d9bd0568c9db63c900a8c8448727af5c58fb043cfeb498f318a90b862" } } ], "extra": [ 1, 33, 133, 136, 181, 222, 123, 144, 38, 56, 85, 5, 193, 13, 109, 111, 190, 174, 99, 227, 225, 116, 184, 67, 34, 147, 209, 169, 55, 44, 126, 243, 234, 2, 17, 0, 0, 0, 7, 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