Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 280e14fe7fe1bd4f59b81bf594b9c58a32947b91237eac2d252ab7c051ddece5

Tx prefix hash: 15a6c9f51b4711ee05a28d9e45db65816eed31b196c0cd89c7c36d7f598c1b57
Tx public key: 80355d90483df5974b2639244bbf22a22c963c9b32df1301891392a3e5bad40e
Timestamp: 1697446261 Timestamp [UCT]: 2023-10-16 08:51:01 Age [y:d:h:m:s]: 01:140:01:10:13
Block: 870784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361091 RingCT/type: yes/0
Extra: 0180355d90483df5974b2639244bbf22a22c963c9b32df1301891392a3e5bad40e021100000005faf35c9c000000000000000000

1 output(s) for total of 0.799339279000 dcy

stealth address amount amount idx
00: cbaa25f1f540f82592f2ef8619c0f0dca268289a1d54ca436debc6e35c1ac6d0 0.799339279000 1325671 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": 870794, "vin": [ { "gen": { "height": 870784 } } ], "vout": [ { "amount": 799339279, "target": { "key": "cbaa25f1f540f82592f2ef8619c0f0dca268289a1d54ca436debc6e35c1ac6d0" } } ], "extra": [ 1, 128, 53, 93, 144, 72, 61, 245, 151, 75, 38, 57, 36, 75, 191, 34, 162, 44, 150, 60, 155, 50, 223, 19, 1, 137, 19, 146, 163, 229, 186, 212, 14, 2, 17, 0, 0, 0, 5, 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