Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2140faf2f6520583516ab3153fbd02dbe84b0414b0d5c824d67a4faefbd109bd

Tx prefix hash: 269f4a1b89ce7611452c4d4779c2857fef0c860a70acb1dfc217b47d7a655cce
Tx public key: 0c70039c25c890cfb7b8a0f916fbe83b548543503bccd1b082a26e30d298987e
Timestamp: 1649654708 Timestamp [UCT]: 2022-04-11 05:25:08 Age [y:d:h:m:s]: 02:258:21:01:46
Block: 477761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704815 RingCT/type: yes/0
Extra: 010c70039c25c890cfb7b8a0f916fbe83b548543503bccd1b082a26e30d298987e0211000000032e6b1fd5000000000000000000

1 output(s) for total of 16.031705158000 dcy

stealth address amount amount idx
00: 454e35066127ba6d505f4be52bea09078d271b854a040b4693f1ff32fbfc7e5b 16.031705158000 898452 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": 477771, "vin": [ { "gen": { "height": 477761 } } ], "vout": [ { "amount": 16031705158, "target": { "key": "454e35066127ba6d505f4be52bea09078d271b854a040b4693f1ff32fbfc7e5b" } } ], "extra": [ 1, 12, 112, 3, 156, 37, 200, 144, 207, 183, 184, 160, 249, 22, 251, 232, 59, 84, 133, 67, 80, 59, 204, 209, 176, 130, 162, 110, 48, 210, 152, 152, 126, 2, 17, 0, 0, 0, 3, 46, 107, 31, 213, 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