Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cac43861ee08fe2fa29f829c5e38f15666d102857374529da5afc3c3806f4bc8

Tx prefix hash: b93a412d944551331b467c0e6d0ef37d4d8aa2dab7fd59ea26adbd69a7c5cfa9
Tx public key: f007cbc2290ba287aebab76c88e98afe708d74ee8ba942d5c75ca6d3d7240241
Timestamp: 1713480551 Timestamp [UCT]: 2024-04-18 22:49:11 Age [y:d:h:m:s]: 01:202:21:17:10
Block: 1003494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403665 RingCT/type: yes/0
Extra: 01f007cbc2290ba287aebab76c88e98afe708d74ee8ba942d5c75ca6d3d7240241021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9a4310ecd0097c28d686d88359c1a22cb42d4f0fdbef36b8fbecc1794464852 0.600000000000 1464036 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": 1003504, "vin": [ { "gen": { "height": 1003494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9a4310ecd0097c28d686d88359c1a22cb42d4f0fdbef36b8fbecc1794464852" } } ], "extra": [ 1, 240, 7, 203, 194, 41, 11, 162, 135, 174, 186, 183, 108, 136, 233, 138, 254, 112, 141, 116, 238, 139, 169, 66, 213, 199, 92, 166, 211, 215, 36, 2, 65, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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