Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9856d6406287330cf11e7cbf5bd7b1d35aaaf52f09b1d15f4c472501c91ca920

Tx prefix hash: 2fde4970c2341851d7b41f3db0d972fb86905b71c2260c0656ff58c915a8b86a
Tx public key: 6b961f403d0992a85ce38e4a5a70a228bdcc1f3ff7cbd1ae0d0f64607b99e179
Timestamp: 1730498034 Timestamp [UCT]: 2024-11-01 21:53:54 Age [y:d:h:m:s]: 00:137:12:44:39
Block: 1144504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98144 RingCT/type: yes/0
Extra: 016b961f403d0992a85ce38e4a5a70a228bdcc1f3ff7cbd1ae0d0f64607b99e179021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a28c5b4c593bae8bcc8b36f21bf2ab2cdf02384e3ea142cce0a6d13bd9ed9f72 0.600000000000 1628739 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": 1144514, "vin": [ { "gen": { "height": 1144504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a28c5b4c593bae8bcc8b36f21bf2ab2cdf02384e3ea142cce0a6d13bd9ed9f72" } } ], "extra": [ 1, 107, 150, 31, 64, 61, 9, 146, 168, 92, 227, 142, 74, 90, 112, 162, 40, 189, 204, 31, 63, 247, 203, 209, 174, 13, 15, 100, 96, 123, 153, 225, 121, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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