Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1084c54e8cdc01ce734fda0bfc28e5761b0253f3a5c119f380d00d9369cf2769

Tx prefix hash: b90ca5f8a389cb651c57e4621ef8d8cb217dbd4d0272b2f9f5cc3b491a2207ad
Tx public key: 6f367e1aa871a83843c844925b65d658ca50b008349d61e9b13675dce624cdca
Timestamp: 1706230431 Timestamp [UCT]: 2024-01-26 00:53:51 Age [y:d:h:m:s]: 01:134:06:09:43
Block: 943371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357095 RingCT/type: yes/0
Extra: 016f367e1aa871a83843c844925b65d658ca50b008349d61e9b13675dce624cdca02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1665c5fbdf51b92f7686c817d2f1e39a3f1c70ce893b4131c8f378d656caa7bc 0.600000000000 1401577 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": 943381, "vin": [ { "gen": { "height": 943371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1665c5fbdf51b92f7686c817d2f1e39a3f1c70ce893b4131c8f378d656caa7bc" } } ], "extra": [ 1, 111, 54, 126, 26, 168, 113, 168, 56, 67, 200, 68, 146, 91, 101, 214, 88, 202, 80, 176, 8, 52, 157, 97, 233, 177, 54, 117, 220, 230, 36, 205, 202, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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