Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5432f42bdf8efc40378336d82e3f9bf58398d0a113ad9572491dcbb40184a85

Tx prefix hash: b138d0c0df13c8edf196a06310eb568d0b50ca39ff5da0f47522e767828d6c00
Tx public key: d7c57284229d9b1da27b66df1b766be85c3e9557cc73dd207e8aa545dce14694
Timestamp: 1751903438 Timestamp [UCT]: 2025-07-07 15:50:38 Age [y:d:h:m:s]: 00:169:12:02:31
Block: 1320708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119610 RingCT/type: yes/0
Extra: 01d7c57284229d9b1da27b66df1b766be85c3e9557cc73dd207e8aa545dce14694021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4a510c09645a6edb92f317ccdcee14a2cef2818044354ce4a18673549fe8b04 0.600000000000 1808409 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 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": 1320718, "vin": [ { "gen": { "height": 1320708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4a510c09645a6edb92f317ccdcee14a2cef2818044354ce4a18673549fe8b04" } } ], "extra": [ 1, 215, 197, 114, 132, 34, 157, 155, 29, 162, 123, 102, 223, 27, 118, 107, 232, 92, 62, 149, 87, 204, 115, 221, 32, 126, 138, 165, 69, 220, 225, 70, 148, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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