Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 464f704c1bac65f9762bd7a298f590a41e3b7933af2832579acc3ad4488657de

Tx prefix hash: 64edb404ec771f026b45d8421e070abdb5202a9d4e7c65806d14d0664769a6cd
Tx public key: fa64100dfaf67f480ce9cc5c44ba8bcf71c59c7829a1d06a7f780d7bae1dd690
Timestamp: 1578863023 Timestamp [UCT]: 2020-01-12 21:03:43 Age [y:d:h:m:s]: 04:318:16:31:23
Block: 44191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117245 RingCT/type: yes/0
Extra: 01fa64100dfaf67f480ce9cc5c44ba8bcf71c59c7829a1d06a7f780d7bae1dd69002110000000f4ac5aa02000000000000000000

1 output(s) for total of 438.104499869000 dcy

stealth address amount amount idx
00: 72363c1cbff55c9cf14faafa511f053d93fad6d330b7b4996e176b9f7c1f6b21 438.104499869000 80343 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": 44201, "vin": [ { "gen": { "height": 44191 } } ], "vout": [ { "amount": 438104499869, "target": { "key": "72363c1cbff55c9cf14faafa511f053d93fad6d330b7b4996e176b9f7c1f6b21" } } ], "extra": [ 1, 250, 100, 16, 13, 250, 246, 127, 72, 12, 233, 204, 92, 68, 186, 139, 207, 113, 197, 156, 120, 41, 161, 208, 106, 127, 120, 13, 123, 174, 29, 214, 144, 2, 17, 0, 0, 0, 15, 74, 197, 170, 2, 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