Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63701ceaa991ea690903843722d187aaa94476629c53f9300914b8bbfc271b3

Tx prefix hash: b75e7a63722a94fbf16021726477ac7139dac326a6b9710ea7953c9e0a060c2b
Tx public key: 9080d89eac24d9f17c61cfa643afe6c63b57cdc9ce85f7645c8be857329a6ee8
Timestamp: 1725266619 Timestamp [UCT]: 2024-09-02 08:43:39 Age [y:d:h:m:s]: 00:213:23:54:15
Block: 1101216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152795 RingCT/type: yes/0
Extra: 019080d89eac24d9f17c61cfa643afe6c63b57cdc9ce85f7645c8be857329a6ee8021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 516c26f3601dac6f2d5e1adb66c4a39fd0298c74d27b0c85bfe595545bbacaa4 0.600000000000 1577201 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": 1101226, "vin": [ { "gen": { "height": 1101216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "516c26f3601dac6f2d5e1adb66c4a39fd0298c74d27b0c85bfe595545bbacaa4" } } ], "extra": [ 1, 144, 128, 216, 158, 172, 36, 217, 241, 124, 97, 207, 166, 67, 175, 230, 198, 59, 87, 205, 201, 206, 133, 247, 100, 92, 139, 232, 87, 50, 154, 110, 232, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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