Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1df92ac4ce4ca92738eb8e8fcf02c95e2ee2ee333937f888ca057f98c8d3a45

Tx prefix hash: 27a07b8298bfe86e6f8f3d01114cfadf9d4bfd88f80813980a966db9a48f740a
Tx public key: a6b0864fa1a9b821048ca5f86ff3f43920d28b75cfc928b399043b4461139d65
Timestamp: 1730691999 Timestamp [UCT]: 2024-11-04 03:46:39 Age [y:d:h:m:s]: 00:147:01:28:28
Block: 1146117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104927 RingCT/type: yes/0
Extra: 01a6b0864fa1a9b821048ca5f86ff3f43920d28b75cfc928b399043b4461139d6502110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b00f66a00f107050de4df3124dfa951118bd8622667a48a7e78f061ba7be62b 0.600000000000 1630682 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": 1146127, "vin": [ { "gen": { "height": 1146117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b00f66a00f107050de4df3124dfa951118bd8622667a48a7e78f061ba7be62b" } } ], "extra": [ 1, 166, 176, 134, 79, 161, 169, 184, 33, 4, 140, 165, 248, 111, 243, 244, 57, 32, 210, 139, 117, 207, 201, 40, 179, 153, 4, 59, 68, 97, 19, 157, 101, 2, 17, 0, 0, 0, 13, 31, 10, 83, 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