Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2771da89fbbfce5859028ee4e2b9e50d9c8e23101da0ba894b480944590b322a

Tx prefix hash: 697eec31d15b7705fcdf3f760569faed08cdff60d3ef11122b7d8e8af22abedc
Tx public key: 555b5938ca01d560ab9f96353af316eaee5363eb6bcc293639a3e66e5ecd203a
Timestamp: 1672876324 Timestamp [UTC]: 2023-01-04 23:52:04 Age [y:d:h:m:s]: 03:073:17:15:45
Block: 667736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 832881 RingCT/type: yes/0
Extra: 01555b5938ca01d560ab9f96353af316eaee5363eb6bcc293639a3e66e5ecd203a02110000000352542ceb000000000000000000

1 output(s) for total of 0.003762819640 xmr

stealth address amount amount idx tag
00: 480f4ad56246d81962d8e9eee9c4fc6513abebe5d6ccad2499ea95a6fae03020 0.003762819640 1108951 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 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": 667746, "vin": [ { "gen": { "height": 667736 } } ], "vout": [ { "amount": 3762819640, "target": { "key": "480f4ad56246d81962d8e9eee9c4fc6513abebe5d6ccad2499ea95a6fae03020" } } ], "extra": [ 1, 85, 91, 89, 56, 202, 1, 213, 96, 171, 159, 150, 53, 58, 243, 22, 234, 238, 83, 99, 235, 107, 204, 41, 54, 57, 163, 230, 110, 94, 205, 32, 58, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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