Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95078d7fbe626dfa81494ffb803bd7593d49d8ce59c9e91a0b135bb9aeeb039a

Tx prefix hash: a360156588add2746220346f2a933e4ddda05f5877308e38104079e91f617333
Tx public key: 2eb003c12b79fb4b4511f91d93cc8de972488b2cd9a1a8a521c8d5bb5e5738d3
Timestamp: 1737090698 Timestamp [UCT]: 2025-01-17 05:11:38 Age [y:d:h:m:s]: 00:156:09:46:12
Block: 1199098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111413 RingCT/type: yes/0
Extra: 012eb003c12b79fb4b4511f91d93cc8de972488b2cd9a1a8a521c8d5bb5e5738d3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 314964e18c2193ad42a4cc35482ebdb6c1e74a9c38dea62f99020ff2cd755694 0.600000000000 1685727 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": 1199108, "vin": [ { "gen": { "height": 1199098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "314964e18c2193ad42a4cc35482ebdb6c1e74a9c38dea62f99020ff2cd755694" } } ], "extra": [ 1, 46, 176, 3, 193, 43, 121, 251, 75, 69, 17, 249, 29, 147, 204, 141, 233, 114, 72, 139, 44, 217, 161, 168, 165, 33, 200, 213, 187, 94, 87, 56, 211, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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