Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e673d3513e76f7d70ec8ca5c1c13c0ed78da9d59d94b02c71a651e40c9dfc81

Tx prefix hash: fde9f102876a4475d65c07fb34fec82d9b68d8f7198064a8d4327b4c4e179368
Tx public key: 1a014f702cce389f21c4dbfebf39a99341f1f67d7a1a8d33b6501a6905abdb4c
Timestamp: 1711893938 Timestamp [UTC]: 2024-03-31 14:05:38 Age [y:d:h:m:s]: 01:340:05:42:29
Block: 990364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501783 RingCT/type: yes/0
Extra: 011a014f702cce389f21c4dbfebf39a99341f1f67d7a1a8d33b6501a6905abdb4c0211000000020011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f4338a5b33fe44fccccaf2a97a73925f583fcc94088b3cf554170057d4fe4d0 0.000600000000 1450686 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 dinastycoin-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": 990374, "vin": [ { "gen": { "height": 990364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f4338a5b33fe44fccccaf2a97a73925f583fcc94088b3cf554170057d4fe4d0" } } ], "extra": [ 1, 26, 1, 79, 112, 44, 206, 56, 159, 33, 196, 219, 254, 191, 57, 169, 147, 65, 241, 246, 125, 122, 26, 141, 51, 182, 80, 26, 105, 5, 171, 219, 76, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369