Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40916cd0224ff81bd8dfef1b1e96bf447ad29e1a43adb7a99e2615ef14f0780b

Tx prefix hash: ec0d743f2d94f8b0cb9262b77353f2e05fe477a2e41047ff5565b8023b1d09ff
Tx public key: d9b43e49c0dc1d3380d87b596336b3178afd136e75b480afb9d91c4b7fc275b4
Timestamp: 1714586249 Timestamp [UTC]: 2024-05-01 17:57:29 Age [y:d:h:m:s]: 02:203:17:47:35
Block: 1012680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 670705 RingCT/type: yes/0
Extra: 01d9b43e49c0dc1d3380d87b596336b3178afd136e75b480afb9d91c4b7fc275b402110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7a2cb46a29f7d4b764bfeb4e54726c6cb45b839a01589bdec68916d02a492b75 0.000600000000 1475280 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": 1012690, "vin": [ { "gen": { "height": 1012680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a2cb46a29f7d4b764bfeb4e54726c6cb45b839a01589bdec68916d02a492b75" } } ], "extra": [ 1, 217, 180, 62, 73, 192, 220, 29, 51, 128, 216, 123, 89, 99, 54, 179, 23, 138, 253, 19, 110, 117, 180, 128, 175, 185, 217, 28, 75, 127, 194, 117, 180, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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) | monero version: