Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58eb81d788073edc58262a4d7bd42302c3c1bceff2c4aaa26e92b8a1ababad58

Tx prefix hash: 40753447a4855213f8894c3ce81f530c29edad2e1ab9a5cdedf39eb6b84098e9
Tx public key: e42dce1e7ff7f905c092e8cb0cc5793e27a7466128f2de21ee31222bf85b0ddc
Timestamp: 1715935766 Timestamp [UCT]: 2024-05-17 08:49:26 Age [y:d:h:m:s]: 00:171:22:01:29
Block: 1023869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123045 RingCT/type: yes/0
Extra: 01e42dce1e7ff7f905c092e8cb0cc5793e27a7466128f2de21ee31222bf85b0ddc02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e081351dca64e4cb4b40811f117fc6429019b78a4ad9bc8d418291293da11aa7 0.600000000000 1489164 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": 1023879, "vin": [ { "gen": { "height": 1023869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e081351dca64e4cb4b40811f117fc6429019b78a4ad9bc8d418291293da11aa7" } } ], "extra": [ 1, 228, 45, 206, 30, 127, 247, 249, 5, 192, 146, 232, 203, 12, 197, 121, 62, 39, 167, 70, 97, 40, 242, 222, 33, 238, 49, 34, 43, 248, 91, 13, 220, 2, 17, 0, 0, 0, 8, 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