Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6725862d83cdf498a4f274a080425072616fd296d29f82037d8eb9812260c0f7

Tx prefix hash: 7b30f0795696a621bafc90d5841afb1a51a91770b8fe89fde7d7a27f61e1e6ad
Tx public key: 512624fa5c6df23361bc0dbc065e287e911da5a582dda89cabaf1e5c8c40991f
Timestamp: 1699452187 Timestamp [UCT]: 2023-11-08 14:03:07 Age [y:d:h:m:s]: 01:154:15:55:18
Block: 887212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371729 RingCT/type: yes/0
Extra: 01512624fa5c6df23361bc0dbc065e287e911da5a582dda89cabaf1e5c8c40991f02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.705177338000 dcy

stealth address amount amount idx
00: 1177d5f8da4c2063f21af65526ca5b1d87e8c7b596c782ad3040c481df3b5a50 0.705177338000 1343073 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": 887222, "vin": [ { "gen": { "height": 887212 } } ], "vout": [ { "amount": 705177338, "target": { "key": "1177d5f8da4c2063f21af65526ca5b1d87e8c7b596c782ad3040c481df3b5a50" } } ], "extra": [ 1, 81, 38, 36, 250, 92, 109, 242, 51, 97, 188, 13, 188, 6, 94, 40, 126, 145, 29, 165, 165, 130, 221, 168, 156, 171, 175, 30, 92, 140, 64, 153, 31, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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