Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdf5328f2e2864044ca5ae17f994f27ccf296ea62fabb975a45aa0cf4d265062

Tx prefix hash: ddad89e0b99837fb2317acde66740eaaac24ad7caa358d8d6a429db2fffe612b
Tx public key: af384622804dd10cb0a3529d95275b1e2811044e0c348b1d1c8345d2e30f72c8
Timestamp: 1581993330 Timestamp [UTC]: 2020-02-18 02:35:30 Age [y:d:h:m:s]: 06:003:20:01:56
Block: 67137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1414371 RingCT/type: yes/0
Extra: 01af384622804dd10cb0a3529d95275b1e2811044e0c348b1d1c8345d2e30f72c8021100000001c71d3ff9000000000000000000

1 output(s) for total of 0.367756464175 xmr

stealth address amount amount idx tag
00: df948f8696155b9bdeb9d0c6d0ef7bd4a3d38d29705bdee84377639a9ebb2e39 0.367756464175 123691 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": 67147, "vin": [ { "gen": { "height": 67137 } } ], "vout": [ { "amount": 367756464175, "target": { "key": "df948f8696155b9bdeb9d0c6d0ef7bd4a3d38d29705bdee84377639a9ebb2e39" } } ], "extra": [ 1, 175, 56, 70, 34, 128, 77, 209, 12, 176, 163, 82, 157, 149, 39, 91, 30, 40, 17, 4, 78, 12, 52, 139, 29, 28, 131, 69, 210, 227, 15, 114, 200, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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