Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4121527fc8e8b1cfd452e9e08987051f4a5f80266005c30a75c20141a0525ad3

Tx prefix hash: bb8f1e764f1ba256c44e3378bcfd9914b0a9270ca782106a88e031d833795515
Tx public key: 9c144b6b4a4aa3173b11dc11c2517c87345a6477c8700d3c06038d41ab1f057b
Timestamp: 1677111330 Timestamp [UCT]: 2023-02-23 00:15:30 Age [y:d:h:m:s]: 02:316:09:24:03
Block: 702869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745525 RingCT/type: yes/0
Extra: 019c144b6b4a4aa3173b11dc11c2517c87345a6477c8700d3c06038d41ab1f057b021100000002faf35c9c000000000000000000

1 output(s) for total of 2.878081827000 dcy

stealth address amount amount idx
00: 1e7b6df4a184cc86f81849f7ddea90ab1e6e6eafcd8ce985c60a38fc8836f1bb 2.878081827000 1146424 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": 702879, "vin": [ { "gen": { "height": 702869 } } ], "vout": [ { "amount": 2878081827, "target": { "key": "1e7b6df4a184cc86f81849f7ddea90ab1e6e6eafcd8ce985c60a38fc8836f1bb" } } ], "extra": [ 1, 156, 20, 75, 107, 74, 74, 163, 23, 59, 17, 220, 17, 194, 81, 124, 135, 52, 90, 100, 119, 200, 112, 13, 60, 6, 3, 141, 65, 171, 31, 5, 123, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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