Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 995eb2b88ed1ff705a807be9c24beccb22262451e8e12e96874bc98d7baf7bc7

Tx prefix hash: f844c4ed96a02bd80d0a74748e5f54f1d1122a69395eec3a1ae309f8483e62e0
Tx public key: b196f669e63a487d00a67a551b56e90cfa2fb4733af5ab7f7d88bda18021160c
Timestamp: 1711074716 Timestamp [UCT]: 2024-03-22 02:31:56 Age [y:d:h:m:s]: 01:014:16:51:41
Block: 983580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271460 RingCT/type: yes/0
Extra: 01b196f669e63a487d00a67a551b56e90cfa2fb4733af5ab7f7d88bda18021160c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35c5e8f8e2242805332933261d78d0275b08d25c47f5ddde8f550edf1df58b99 0.600000000000 1443721 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": 983590, "vin": [ { "gen": { "height": 983580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35c5e8f8e2242805332933261d78d0275b08d25c47f5ddde8f550edf1df58b99" } } ], "extra": [ 1, 177, 150, 246, 105, 230, 58, 72, 125, 0, 166, 122, 85, 27, 86, 233, 12, 250, 47, 180, 115, 58, 245, 171, 127, 125, 136, 189, 161, 128, 33, 22, 12, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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