Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb42aff5d4d28e932866f3ce089f335abc56f009a8078e11a540d42c74003cd0

Tx prefix hash: 988c15d6f75521bfb810fff7871be9694efc46a7f782a12fa2be91afe41507ac
Tx public key: 5fa15c6b39c1cbc07a5a329bf9f7705dfe4e690ab43918f882d0653a9f35aa4a
Timestamp: 1660029580 Timestamp [UCT]: 2022-08-09 07:19:40 Age [y:d:h:m:s]: 02:160:15:16:29
Block: 561940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 636239 RingCT/type: yes/0
Extra: 015fa15c6b39c1cbc07a5a329bf9f7705dfe4e690ab43918f882d0653a9f35aa4a0211000000016570b1ef000000000000000000

1 output(s) for total of 8.434505434000 dcy

stealth address amount amount idx
00: bc64433796a904593c5a7ac3e740ece77136a62d815f696ffd7ed11a35327386 8.434505434000 994464 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 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": 561950, "vin": [ { "gen": { "height": 561940 } } ], "vout": [ { "amount": 8434505434, "target": { "key": "bc64433796a904593c5a7ac3e740ece77136a62d815f696ffd7ed11a35327386" } } ], "extra": [ 1, 95, 161, 92, 107, 57, 193, 203, 192, 122, 90, 50, 155, 249, 247, 112, 93, 254, 78, 105, 10, 180, 57, 24, 248, 130, 208, 101, 58, 159, 53, 170, 74, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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