Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faf901038efb40cab434bd62c7683fb0ba7260d61efe7fcf3be11b05b2c91ea1

Tx prefix hash: 3054ae5469ce589b04fb22f778f1d13f03379c51a3f74aed168043d1a218b282
Tx public key: fb9b0d07289575ae4dd7638e96c93f2e45c8ca1e015a8096c1e58182c60c25c7
Timestamp: 1727997601 Timestamp [UCT]: 2024-10-03 23:20:01 Age [y:d:h:m:s]: 00:051:18:27:19
Block: 1123859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36982 RingCT/type: yes/0
Extra: 01fb9b0d07289575ae4dd7638e96c93f2e45c8ca1e015a8096c1e58182c60c25c702110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68138646a3c08ec54782d7f0bcccccd2db992aaeaa7c0f1e865af48a280851a6 0.600000000000 1606398 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": 1123869, "vin": [ { "gen": { "height": 1123859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68138646a3c08ec54782d7f0bcccccd2db992aaeaa7c0f1e865af48a280851a6" } } ], "extra": [ 1, 251, 155, 13, 7, 40, 149, 117, 174, 77, 215, 99, 142, 150, 201, 63, 46, 69, 200, 202, 30, 1, 90, 128, 150, 193, 229, 129, 130, 198, 12, 37, 199, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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