Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2457efcca2371e11e42675a6a041093a96744a90ec100e15f2b343f5fd09205d

Tx prefix hash: dffa41a4f97c823141064528d59201552341181a76d193a42dc30825dab97c14
Tx public key: 17f9756cda9bf23af2a3e0e9fd3cd749bdb848276f02aa0131a40d8a395f239d
Timestamp: 1706872188 Timestamp [UCT]: 2024-02-02 11:09:48 Age [y:d:h:m:s]: 01:027:12:11:02
Block: 948714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280688 RingCT/type: yes/0
Extra: 0117f9756cda9bf23af2a3e0e9fd3cd749bdb848276f02aa0131a40d8a395f239d02110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 532a28019e1c7570d6e2527a9b5f3c54e9a8ebaa689c8746e94e572092e017dd 0.600000000000 1407180 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": 948724, "vin": [ { "gen": { "height": 948714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "532a28019e1c7570d6e2527a9b5f3c54e9a8ebaa689c8746e94e572092e017dd" } } ], "extra": [ 1, 23, 249, 117, 108, 218, 155, 242, 58, 242, 163, 224, 233, 253, 60, 215, 73, 189, 184, 72, 39, 111, 2, 170, 1, 49, 164, 13, 138, 57, 95, 35, 157, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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