Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d709f78c27684ccd5c65867d7a3638d80f465c4cc76e11c0ac320b787d07adf

Tx prefix hash: 1b72e047d4f90868c9e3eed3c3101e49143dabb7aa5490017e8af553564e1176
Tx public key: a1e771d70d732d2c84a62a75c193f71f629ff57475f83aed7f3c1891dddf5f42
Timestamp: 1672851736 Timestamp [UCT]: 2023-01-04 17:02:16 Age [y:d:h:m:s]: 02:006:22:38:01
Block: 667546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526857 RingCT/type: yes/0
Extra: 01a1e771d70d732d2c84a62a75c193f71f629ff57475f83aed7f3c1891dddf5f4202110000000252542ceb000000000000000000

1 output(s) for total of 3.768278143000 dcy

stealth address amount amount idx
00: 36883321a050b0ae165983c1b1e859242b13e60ec18203267e2106c936ce13e4 3.768278143000 1108759 of 0

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": 667556, "vin": [ { "gen": { "height": 667546 } } ], "vout": [ { "amount": 3768278143, "target": { "key": "36883321a050b0ae165983c1b1e859242b13e60ec18203267e2106c936ce13e4" } } ], "extra": [ 1, 161, 231, 113, 215, 13, 115, 45, 44, 132, 166, 42, 117, 193, 147, 247, 31, 98, 159, 245, 116, 117, 248, 58, 237, 127, 60, 24, 145, 221, 223, 95, 66, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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