Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cd1590b7b09b7feef907ce427b06d314c26a4cd6721f7c44dd048461a504121

Tx prefix hash: f68dcccf6fafdebfbdaa977f0b7bf5bcc04a6a927c329c8f94e385fc7b785f82
Tx public key: 0cd45894a70759ca44245557d8df1ac1603294253f9a0f85eef53d32b3d68449
Timestamp: 1579235930 Timestamp [UTC]: 2020-01-17 04:38:50 Age [y:d:h:m:s]: 06:033:13:59:11
Block: 47332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1432609 RingCT/type: yes/0
Extra: 010cd45894a70759ca44245557d8df1ac1603294253f9a0f85eef53d32b3d68449021100000004dcee4b4d000000000000000000

1 output(s) for total of 0.427730552226 xmr

stealth address amount amount idx tag
00: 0674ea233d249c5749d053781d7776b1e1e311ecab6f7c7f5a8cec4e3c6e3db1 0.427730552226 87467 of 0 -

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 dinastycoin-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": 47342, "vin": [ { "gen": { "height": 47332 } } ], "vout": [ { "amount": 427730552226, "target": { "key": "0674ea233d249c5749d053781d7776b1e1e311ecab6f7c7f5a8cec4e3c6e3db1" } } ], "extra": [ 1, 12, 212, 88, 148, 167, 7, 89, 202, 68, 36, 85, 87, 216, 223, 26, 193, 96, 50, 148, 37, 63, 154, 15, 133, 238, 245, 61, 50, 179, 214, 132, 73, 2, 17, 0, 0, 0, 4, 220, 238, 75, 77, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369