Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e359c7d22a9c33e1801331bcb808cbf013c12768a6757108a479ca9647f2397

Tx prefix hash: 3b90f4c937bdc54f3d23a5841e8b074097f2c144202d9746816a4d34167e7092
Tx public key: b19bf31c6a07bcf8e9a69934dfea19ff5d1ee8e330a8b3d4115b44fb845c7834
Timestamp: 1737658391 Timestamp [UCT]: 2025-01-23 18:53:11 Age [y:d:h:m:s]: 00:144:23:35:52
Block: 1203759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103356 RingCT/type: yes/0
Extra: 01b19bf31c6a07bcf8e9a69934dfea19ff5d1ee8e330a8b3d4115b44fb845c7834021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbe869b2b04116c3a6084b8de5021b2a59673db5da92a34190428311b8713ba8 0.600000000000 1690438 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": 1203769, "vin": [ { "gen": { "height": 1203759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbe869b2b04116c3a6084b8de5021b2a59673db5da92a34190428311b8713ba8" } } ], "extra": [ 1, 177, 155, 243, 28, 106, 7, 188, 248, 233, 166, 153, 52, 223, 234, 25, 255, 93, 30, 232, 227, 48, 168, 179, 212, 17, 91, 68, 251, 132, 92, 120, 52, 2, 17, 0, 0, 0, 2, 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