Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07a0700a5d267b152ef5ed8788e3579c46798029600b46b5d768ca1a7f923125

Tx prefix hash: 1441f42f139379204e08884b0b4faac592295b7c704711e825ffaa47c25defbd
Tx public key: bd919b2a0b82d2a6241d7553f5afe12696407be481d4f21a4a44deb41cdbb148
Timestamp: 1717464618 Timestamp [UCT]: 2024-06-04 01:30:18 Age [y:d:h:m:s]: 00:145:05:50:51
Block: 1036537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104001 RingCT/type: yes/0
Extra: 01bd919b2a0b82d2a6241d7553f5afe12696407be481d4f21a4a44deb41cdbb1480211000000014385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd1fe9f70d37fe07c39b3d2bc8dfaf87b3f455af51c37f9b17a14b0515c9e4c6 0.600000000000 1505064 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": 1036547, "vin": [ { "gen": { "height": 1036537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd1fe9f70d37fe07c39b3d2bc8dfaf87b3f455af51c37f9b17a14b0515c9e4c6" } } ], "extra": [ 1, 189, 145, 155, 42, 11, 130, 210, 166, 36, 29, 117, 83, 245, 175, 225, 38, 150, 64, 123, 228, 129, 212, 242, 26, 74, 68, 222, 180, 28, 219, 177, 72, 2, 17, 0, 0, 0, 1, 67, 133, 54, 42, 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